@hoandco I don't think so. I can hardly follow your comments. To get clear, pleas post the "DNS Server Settings" from System > General Setup. And what do you get exactly, when doing a lookup for google.com in Diagnostics > DNS Lookup? Do you have the DNS Resolver enabled on pfSense?

@Bummer : did your import config file to 64bit version wokred?

@Gektor the patch in that thread should fix it.

@Lavarocker said in OpenVPN Issues Anyone After Upgrading to 23.05?: Re: To 23.05 or not ? that is the question :) Has anyone tested OpenVPN after upgrading to 23.05? The last official update broke it. Thanks I have issue with my OpenVPN Server and client. I was able to get OpenVPN Server working again by disable it and then re-enable it. As for my 2 OpenVPN clients, both show are connected but the gateway show offline/packetloss. I have rebuild it again since I can't fine any issue. My suggest is that there likely some new field being added to OpenVPN which causing issue on my end.

@NollipfSense said in Lock Top navigation...?: @furom You could restart webGUI at the console or reboot. Cool! I was logged out and when logging back in it stuck! Thanks :)

@TheRedHerring Ah but devices go around DNS with DOH.Browsers use it by default. I’ve one device that requires it. This is an overly detailed guide but may help with blocking other DNS if that’s your goal: https://jpgpi250.github.io/piholemanual/doc/Block%20DOH%20with%20pfsense.pdf

After running around in circles for almost a week, trying all suggestions on the forum I finally got it working. The solution? Using the console and 13) Update from console

I would go with a small unit that comes with 3 LAN ports and having an looking eye forward it should maybe coming by site with 3 x 2.5 GBit/s ports. WAN /LAN /DMZ / (WLAN) CPU 4C/4T w/ 4 GB RAM CPU 4C/8T w/ 8 GB RAM Or if the RAM module will be able to change it may be the best option! (SO-DIMM) If you need a fall back line (3G/LTE) it should comes sorted with an SIM socket and/or miniPCIe or M.2 socket inside. If you want to use the captive portal with FreeRadius it should be also sorted with a miniPCIe or M.2 for a wireless card (WiFi) It should be able to connect to the console in any kind. Serial DB9-RS232 or RJ45 CON or USB CON port. For solving out any problems. Netgate itself are offering smaller units in their shop. Perhaps there is something for your needs in? Have look please: Netgate Shop What is your entire WAN speed? What packages will you run? Do you using PPPoE?

@Gektor Sounds similar but different situation. New thread? Check the logs to see why PHP is crashing.

Have you tried to set the latency to a different mode?

Quick update: I have decided to try reinstalling pfsense on ZFS instead of UFS. I backed up all my configs first, did a clean install with 1 striped disk and set zfs copies=2. It hasn't been long since I restored everything but pfsense has been running for 16 hours now without any crashes so it's looking promising so far. I will post another update with how it's running after a few days or when it crashes again.

@Sorjal said in Errors that occurred during upgrades to 23.01 and 23.05 RC: I try to switch away from 192.x.x.x A good idea in most cases.

@tibtub On a 2100 you have to time it right. https://docs.netgate.com/pfsense/en/latest/solutions/netgate-2100/factory-reset.html (lurkers: some other models that button just reboots) Or use the console menu option to reset, or web GUI Diagnostics menu to reset.

Try the fix outlined in this thread and post: https://forum.netgate.com/topic/180313/firewall-alias-import-bug-after-upgrade-to-23-05-release-amd64/3.

@jimp said in Firewall Alias import bug after upgrade to 23.05-RELEASE (amd64): I committed a fix for this: https://github.com/pfsense/pfsense/commit/217f42ec30a4008907ac6fbb65b7b2e0ebf51eb9 That is a nasty bug. Never thought I would use vim one day.

@mathomas3 said in 5G modems with Fanless Computer: @Dobby_ The reason why I am using this solution is that my provider requires the use of their hardware... should I put the SIM into something different would violate the TOS... Ah, ok this was not clear to me.

ix0@pci0:1:0:0: class=0x020000 card=0x7b118086 chip=0x154d8086 rev=0x01 hdr=0x00 vendor = 'Intel Corporation' device = 'Ethernet 10G 2P X520 Adapter' class = network subclass = ethernet ix1@pci0:1:0:1: class=0x020000 card=0x7b118086 chip=0x154d8086 rev=0x01 hdr=0x00 vendor = 'Intel Corporation' device = 'Ethernet 10G 2P X520 Adapter' class = network subclass = ethernet

@captain351 So your devices are obviously using WINS for name resolution. Why don't you move over to DNS? Since you probably run a DHCP server on pfSense you can configure it to register the host names in the DNS server directly. So all devices would be able to resolve the host names.